Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Aug 19, 2009, 7:40:16 PM (14 years ago)
- Author:
-
Maiku
- Comment:
-
Updated VV FAQs
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v171
|
v172
|
|
111 | 111 | Pidgin can only use saved states for Auto Away. You need to create and save a named state first. |
112 | 112 | |
113 | | == Voice and Video (Microphone and Webcam) Support (Not Implemented Yet) == |
| 113 | == Voice and Video (Microphone and Webcam) Support == |
114 | 114 | |
115 | 115 | === Does Pidgin support webcams (video)? === |
| 116 | Yes, but only for XMPP/GMail. |
116 | 117 | === Does Pidgin support MSN video chat? === |
117 | 118 | Not currently. It is planned. See below. |
118 | 119 | |
119 | 120 | === Does Pidgin support microphones (voice)? === |
| 121 | Yes, but only for XMPP/GMail/GTalk. |
120 | 122 | === Does Pidgin support libjingle? === |
121 | | Not currently. It is planned. See below. |
122 | | |
123 | | === When will voice and video be implemented? === |
| 123 | Yes, both GMail and GTalk implementations should work. |
| 124 | |
| 125 | === How do I configure my microphone/webcam? === |
| 126 | Currently, the command-line gstreamer-properties program is used. This is only available on GNOME-based systems. On other systems, Pidgin makes its best guess as to which device to use. A plugin is planned to support this functionality on other systems. |
| 127 | |
| 128 | === When will voice and video be implemented on other protocols? === |
124 | 129 | We plan to implement these features eventually, but it is a daunting task. Not all of our developers care about these features, and because of that don't want to work on them. The time available to those developers who do want to work on these features is limited, and so any work on these features proceeds slowly. |
125 | | |
126 | | We aim to have an abstracted, protocol-agnostic API for voice and video, which makes the task harder. Also adding to the difficulty is that now that we have a completely split core (libpurple) and UI (Pidgin and Finch), we refuse to take a step backward and violate this split. The protocol plugins can NOT have any code in them that is UI-dependent, or we break the libpurple/UI split. This imposes additional restrictions that make it a very painstaking process to implement voice and video correctly. |
127 | 130 | |
128 | 131 | In short, we have no idea when this will happen. It could be tomorrow, or it could be in 2099. That's really the best answer we can give right now. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!